You are right, it's not smart.

What about the "+" sign ?

PS: this is ticket #223 
(http://zena.lighthouseapp.com/projects/2549-zena/tickets/223 
)

Gaspard

On 6 oct. 08, at 20:54, [EMAIL PROTECTED] wrote:

>
> I use, windows, osx, linux for development, just currently at my "¤"#
> ¤"%¤ Vista laptop...
> But still it's unsmart to have that type of filenames, they are bound
> to be trubble...
>
> But I am looking foward to play with it, more, when I get the time..
>
> regards
> svend
>
> On Oct 6, 8:43 pm, Gaspard Bucher <[EMAIL PROTECTED]> wrote:
>> Damn !
>>
>> I did not suspect that having stars "*" in the filenames would cause
>> such troubles. I cannot simply rename these files since the
>> name is used as the template definition:
>>
>> [class]-[mode]-[format].zafu
>>
>> An modes with "*" exist inside zena and are used to render special
>> pages (search result, admin layout, index page). The star is there so
>> that
>> these modes cannot be used to display arbitrary pages (ex. /
>> page43_*index.html will not work).
>>
>> You could try to use the archive until I find a better prefix that
>> does not cause these problems.
>>
>> The compressed version is at:http://zenadmin.org/zena.tgz
>>
>> Beware though that zena has never been used on a windows box before
>> and you might find lots of surprises like this one. To avoid loosing
>> time with installation issues, I would recommend installing a simple
>> debian box with vmware...
>>
>>
>>
>>> I am having problems both with Git and SVN on Vista.
>>> Both are install correct, the problem seems to come from the
>>> repository.
>>
>>> This is the svn output:
>>> A    trunk\db\init
>>> A    trunk\db\init\base
>>> A    trunk\db\init\base\help.fr.zml
>>> A    trunk\db\init\base\skins
>>> A    trunk\db\init\base\skins\default
>>> svn: Can't check path 'trunk\db\init\base\skins\default\Node-
>>> *popupLayout.zafu':
>>> The filename, directory name, or volume label syntax is incorrect.
>>
>>> regards
>>> svend
>>
>>> On Oct 6, 4:33 pm, Gaspard Bucher <[EMAIL PROTECTED]> wrote:
>>>>> Fun, source code to read!
>>
>>>> The code started with rails 0.9.x (end 2005) and some parts reflect
>>>> this old history...
>>
>>>> Some interesting parts:
>>
>>>> lib/query_builder (pseudo sql query builder)
>>>> lib/parser, lib/parser/lib/rules/zafu.rb (template parser)
>>
>>>> test/helpers/zena_parser/*.yml (yaml tests for templates)
>>>> test/helpers/query_builder/*.yml (yaml tests for pseudo sql)
>>
>>>> Do not hesitate to ask questions...
>>
>>>> Gaspard
>>
>>>>> On Oct 6, 6:09 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
>>>>> wrote:
>>>>>> looks impressive.
>>>>>> I am looking foward to testing the CMS.
>>
>>>>>> regards
>>>>>> svend
>>
>>>>>> On Oct 6, 10:09 am, "Gaspard Bucher" <[EMAIL PROTECTED]> wrote:
>>
>>>>>>> After 3 years of work in my cave, I am happy to go out in the
>>>>>>> sunlight
>>>>>>> to announce the first public beta release of zena !
>>
>>>>>>> In a few words:
>>
>>>>>>> Zena is a CMS based on ruby on rails with a very advanced xhtml
>>>>>>> based
>>>>>>> templating language called zafu. Sites have been running in
>>>>>>> production
>>>>>>> mode for nearly 2 years now, so it's quite stable (more then  
>>>>>>> 1340
>>>>>>> unit
>>>>>>> tests).
>>
>>>>>>> One of the most important architecture aspects of this CMS is  
>>>>>>> that
>>>>>>> it
>>>>>>> is based on Single Table Inheritance with the ability to create
>>>>>>> custom
>>>>>>> classes from the web frontend.
>>
>>>>>>> More information on this release in this post from the 
>>>>>>> blog:http://zenadmin.org/473
>>
>>>>>>> Videos:http://zenadmin.org/426
>>
>>>>>>> I hope you enjoy...
>>
>>>>>>> Gaspard
> >


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to