Hannes,
Happy to help, at least with some ideas. Brea is still an early
prototype, but suit my needs without the burden of all the extra stuff
Seaside includes, for simple cases as mine, but if glad to know that it
works for your use case.
Cheers,
Offray
On 05/10/17 10:49, H. Hirzel wrote:
> H
Hello Offray
Thank you for making the Brea wiki code available. I have read it and
got some ideas out of it.
My conclusion was that I do not have the capacity at the moment to
continue working on it.
So I went for Seaside though the library is large. It has a simple
wiki as well. And with Pier a
Hi,
On 06/09/17 02:12, H. Hirzel wrote:
> So at the moment I am fine to get it up and running using a FossilRepo.
> Later on I will work on replacing it with a JSON data store.
Please let me know if you need any permissions into the repository to
make JSON data store available in Brea.
>
> On 9
So at the moment I am fine to get it up and running using a FossilRepo.
Later on I will work on replacing it with a JSON data store.
On 9/6/17, H. Hirzel wrote:
> I understand that it makes a lot of sense to reuse the functions
> implemented in the FossilRepo.
>
> Installation of the Fossil vers
I understand that it makes a lot of sense to reuse the functions
implemented in the FossilRepo.
Installation of the Fossil version control system seems to be very
simple, just put a single executable file into the pharo folder for
example
https://fossil-scm.org/index.html/doc/trunk/www/index.wi
What I wanted to write is that the class FossilRepo is not included.
And that the setup of the Teapot server should not be hidden in lazy
initialisation method but made explicit with some methods in a method
category called 'setup' or 'configuration'.
HH
On 9/6/17, H. Hirzel wrote:
> Hi Offray
Hi Offray
Thank you for answering and the new release. I will look at it in
detail. Here is a first feedback.
On 9/6/17, Offray Vladimir Luna Cárdenas wrote:
> Hi, Hannes,
>
> Sorry it took so long.
No problem. It was actually less than 14 days which is not long .
:-)
> I'm now finishing
Hi, Hannes,
Sorry it took so long. I'm now finishing my PhD and entering into a
focused writing mode, so is difficult to keep with mailing lists these
days.
New version contains an example. Please load the ConfigurationOfBrea as
showed in http://ws.stfx.eu/9MQGFUQ909BW and after that run:
BreaWe
Hannes,
Fossil give me distributed wiki support out of the box, but the content stored
there are just STON serialized objects, so maybe this can work also for your
JSON needs.
Next week I'll have more code.
Cheers,
Offray
El 24 de agosto de 2017 4:30:37 GMT-05:00, "H. Hirzel"
escribió:
>Of
Offray
Thanks for the two answers and in particular.
Fossil is as a data store and version control system is a good solution.
But I have to use a JSON data store. So my interest is that I can hook
that up to Brea.
(or as a first step just keep the objects in the image -- image persistence)
Next w
Meanwhile, you can check at [1], a Grafoscopio notebook where I documented Brea
and the problem is trying to solve.
[1] http://mutabit.com/repos.fossil/gig/dir?ci=tip
Cheers,
Offray
El 23 de agosto de 2017 20:15:38 GMT-05:00, Offray
escribió:
>Hi Hannes,
>
>I will improve docs and test, but
Hi Hannes,
I will improve docs and test, but for the moment I'll be away of my computer at
least until Friday. Image persistance is not implemented.
Cheers,
Offray
El 23 de agosto de 2017 13:44:46 GMT-05:00, "H. Hirzel"
escribió:
>On 8/23/17, Offray wrote:
>> Hi,
>>
>> On the Teapot + Musta
On 8/23/17, Offray wrote:
> Hi,
>
> On the Teapot + Mustache integration, Hannes, you may want to see my early
> prototype:
>
> http://smalltalkhub.com/#!/~Offray/Brea
>
> At some point, it will contain distributed wiki, backed by Fossil, now that
> we're thinking in empower community driven wiki
13 matches
Mail list logo
