http://blog.gmane.org/gmane.comp.lang.smalltalk.smallwiki hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.comp.lang.smalltalk.smallwiki/1898 Hi, I would like to give the Google Webmaster Tools a try, and for that I need to authenticate that I am the owner of the site. For this to happen, I need to add a meta tag in my Pier pages. The only way I know is to go add it in the updateRoot method, but this should be supported by Pier at a user level. Is there a way to do this? If not, what would be the possible solutions? Cheers, Doru -- www.tudorgirba.com www.tudorgirba.com/blog "Every now and then stop and ask yourself if the war you're fighting is the right one." _______________________________________________ SmallWiki, Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki Tudor Girba 2008-05-17T10:26:27 http://comments.gmane.org/gmane.comp.lang.smalltalk.smallwiki/1897 _______________________________________________ SmallWiki, Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki Esteban Lorenzano 2008-05-07T19:17:25 http://comments.gmane.org/gmane.comp.lang.smalltalk.smallwiki/1896 Suppose I have a hierarchy like this: Object subclass: #ClassA instanceVariableNames: 'name' classVariableNames: '' poolDictionaries: '' category: 'Example' ClassA subclass: #ClassB instanceVariableNames: 'bInstVar' classVariableNames: '' poolDictionaries: '' category: 'Example' ClassB subclass: #ClassC1 instanceVariableNames: 'c1InstVar' classVariableNames: '' poolDictionaries: '' category: 'Example' ClassB subclass: #ClassC2 instanceVariableNames: 'c2InstVar' classVariableNames: '' poolDictionaries: '' category: 'Azteca-Model' ClassA is just an abstract parent with the common functionality for the other classes. Same for ClassB. Only objects from ClassC1 and ClassC2 are to be created. Should I create a "descriptionName" method in the class side of ClassA to be inherited for ClassC1 and ClassC2 or should I create a "descriptionName" once for each of ClassC1, ClassC2. The same question about the inst vars for ClassB. Summary, when you have a previously created hierarchy of classes a Miguel Enrique Cobá Martínez 2008-05-05T23:28:43 http://comments.gmane.org/gmane.comp.lang.smalltalk.smallwiki/1893 _______________________________________________ SmallWiki, Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki Dario Trussardi 2008-05-05T14:51:30 http://comments.gmane.org/gmane.comp.lang.smalltalk.smallwiki/1892 _______________________________________________ SmallWiki, Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki Dario Trussardi 2008-05-05T13:46:08 http://comments.gmane.org/gmane.comp.lang.smalltalk.smallwiki/1890 Hi, I just noticed that Google Reader does not manage to read a Pier blog. I tried with both ming and Lukas, and it finds "no items". Any idea why? Cheers, Doru -- www.tudorgirba.com www.tudorgirba.com/blog "When people care, great things can happen." _______________________________________________ SmallWiki, Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki Tudor Girba 2008-05-03T20:45:58 http://comments.gmane.org/gmane.comp.lang.smalltalk.smallwiki/1889 There are new versions of both Smallwiki and Smallwiki SCG on Bern Store Changes Smallwiki - Metatag Redirect - Metatag Custom RSS - RSS fix moved here from Smallwiki SCG Changes Smallwiki SCG - Using new Google Analytics script - No analytics for internal and logged in users - Logged in users have access to internal pages Alas I was not able to checkout Smallwiki in a fresh image to run the test (in the SCG wiki 9 tests fail due to changes in Smallwiki SCG). There seems to be an issue with Store and version ids. cheers, AA _______________________________________________ SmallWiki, Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki Adrian Kuhn 2008-05-01T20:33:20 http://comments.gmane.org/gmane.comp.lang.smalltalk.smallwiki/1887 _______________________________________________ SmallWiki, Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki Dario Trussardi 2008-04-30T20:13:32 http://comments.gmane.org/gmane.comp.lang.smalltalk.smallwiki/1883 _______________________________________________ SmallWiki, Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki Dario Trussardi 2008-04-29T10:10:34 http://comments.gmane.org/gmane.comp.lang.smalltalk.smallwiki/1880 Hello Lukas, I discovered that where MAReport-renderContentOn: creates a table with an ajaxId. If you try to use a scriptaculous updater on this id it works in firefox, but not in ie6. So it looks like we need an enclosing div cheers Keith _______________________________________________ SmallWiki, Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki Keith Hodges 2008-04-29T01:23:19 http://comments.gmane.org/gmane.comp.lang.smalltalk.smallwiki/1879 _______________________________________________ SmallWiki, Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki Dario Trussardi 2008-04-28T20:58:33 http://comments.gmane.org/gmane.comp.lang.smalltalk.smallwiki/1878 _______________________________________________ SmallWiki, Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki Dario Trussardi 2008-04-26T14:36:10 http://comments.gmane.org/gmane.comp.lang.smalltalk.smallwiki/1874 I had some thing strange going on... I had lots of instances of PRDocument, at one point it reported 88000... The key to clearing them out appeared to be, re-initializing, PRMacroExpander, Inspecting PRMacroExpander default, the #table dictionary of blocks, those blocks had temps, with a #context defined, and that context had properties etc... still it freed up 100Mb... Keith _______________________________________________ SmallWiki, Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki Keith Hodges 2008-04-23T23:52:57 http://comments.gmane.org/gmane.comp.lang.smalltalk.smallwiki/1871 _______________________________________________ SmallWiki, Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki Dario Trussardi 2008-04-23T15:43:22 http://comments.gmane.org/gmane.comp.lang.smalltalk.smallwiki/1868 When a PRPage is initialized it has a #document if however you edit that document and make it empty, the #document disappears, and #hasDocument reports false, even though it does really have a document, but it is empty. Keith _______________________________________________ SmallWiki, Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki Keith Hodges 2008-04-23T03:35:12 http://comments.gmane.org/gmane.comp.lang.smalltalk.smallwiki/1867 Hello Lukas, The hierarchy of choices available as swappable replacements for PRPierFrame, is starting to mature. The first, PRPierFrameCentral, implements the wiring in order for it to be the centre of attention as I suggested yesterday. It aims to preserve the existing behaviour, however it has a nice innovation: If your site has no environment at all, it caches one for you. i.e. your layout can be provided as part of your PRPierFrame subclass, and does not need to be user visible or editable. If you edit the code that generates your layout directly, it will get used for the next session. And that's not all. If you add an empty page, and set that as an environment in a structure's settings, it will automatically populate. == The second class PRPierBasicBP moves the layout to: /environment/layout /environment/style Again it will be cached for you "off-site" until an environment is added. == A third class PRPierBasicCWS is a first attempt at an alternative to blueprint. == A fourth class is P Keith Hodges 2008-04-23T05:12:36 http://comments.gmane.org/gmane.comp.lang.smalltalk.smallwiki/1861 Hello Lukas, I am curious as to what purpose this serves in the following method. any clues? Keith ------- WAPierFrame-updateRoot: aHtmlRoot .....most of the method snipped.... "I have no idea what this library thing is?" (self environment propertyAt: #library ifAbsent: [ ^ self ]) default updateRoot: aHtmlRoot _______________________________________________ SmallWiki, Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki Keith Hodges 2008-04-22T03:38:28 http://comments.gmane.org/gmane.comp.lang.smalltalk.smallwiki/1860 Dear Lukas, I think I am getting there... One thing Pier has been lacking is a simple means of packaging up a configuration of Pier as a simple module. Important methods for setting things up, such as #defaultEnvironment are on PRStructure of all places! Styles are here, layouts are there, and content is yet somewhere else (PRKernel class defaultRoot). I have tried out a solution! Route everything through the PRPierFrame, then you can pick a PRFrame subclass in seaside/config, or embed it in another Seaside application. 1. Style Libraries (currently manually added in seaside/config) 2. Script Libraries (currently manually added in seaside/config) 3. Policy for finding Layout from the structure. (currently in PRStructure) 4. Policy for finding StyleSheets (currently in PRStructure) 5. Default Environment (currently in PRStructure) 6. Default Layout (currently in PRStructure) 7. Default Kernel Content (currently in PRKernel class) 8. Not Found Handler (currently in PRMain) 9. Forbidden Handler (curre Keith Hodges 2008-04-22T07:34:34 http://comments.gmane.org/gmane.comp.lang.smalltalk.smallwiki/1853 I am a bit stuck in a pre-Blueprint world. So I was having a look at it. I loaded up the current, release of pier, and it is very clean and ready to be styled. I miss the tree view, has it gone because it doesnt fit in the layout? Blueprint looks cool for some applications. I have one site which has a fairly fixed layout, so blueprint appears to me to be an ideal solution for that, but not, I fear for pier in general. This appears to me to be a better fit, for general blogish/corporate sites. http://www.contentwithstyle.co.uk/Articles/17/a-css-framework/ best regards Keith _______________________________________________ SmallWiki, Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki Keith Hodges 2008-04-21T18:43:34 http://comments.gmane.org/gmane.comp.lang.smalltalk.smallwiki/1852 _______________________________________________ SmallWiki, Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki Jacobsen Jörg 2008-04-18T12:20:25 http://comments.gmane.org/gmane.comp.lang.smalltalk.smallwiki/1845 I am interested to know how people are managing to style Magritte Forms. I don't know if attachments get through but I have attached an image of what I have managed to achieve so far... I dont know much about css, but I assumed that it was not possible to take the tables of field key/values generated by magritte and to move things around as much as I would like. I produced my own renderer which renders the key/values, using divs. However I still have some problems. For example, the "Confirm" "Cancel" buttons are rendered outside of the form as a decoration. As such they have no knowledge of the form that they are operating on, and so render without any identifiable "class". Style applied to them applies to all uses of "Confirm"/"Cancel" buttons. It looks to me like some re-architecting is needed here, its not that I dont like the use of the decorator in this instance. I am thinking that this is another instance where the lack of child parent communication is a problem. regards Keith _______ Keith Hodges 2008-04-17T17:55:39 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.lang.smalltalk.smallwiki