Re: [Pharo-users] Magritte extension
Hi all, It has been a while that I was really involved in developing on (QC)Magritte and doing stuff on the web ... I am all in favour of forming a group of active people to do some improvements on Magritte. I wrote on my todo list that I should feed back some of the improvements made in QCMagritte back to Magritte, but feeling a lack of interest from the community it dropped of my list. Maybe now is a good time to find some room in my schedule for doing so. First of all I want to advertise QCMagritte: This framework is easy to use. It has a seaside like tutorial, that every developer should be able to follow without any significant problems and shows all significant features of both Magritte, Seaside and QCMagritte. Although it lacks documentation on the technical details of the framework, it has documentation included how to use the framework (as a developer). Secondly. I agree that the most easy customisation of Magritte is using custom components. The Magritte components provided are quite basic. That is why in QCMagritte there is a number of components included that support AJAX functionality. It also contains a component that allows inline editing in a report. The idea about Magritte is also that the descriptions do not require a certain set of components. I.e. there was also an attempt on creating a Morph set of components ... that is a bit incomplete. Third. Feeding the improvements I have made in QC Magritte back into Magritte should probably be discussed this on the Magritte mailinglist. So I will do this in a separate post, mailing to bost lists. Cheers, Diego -- View this message in context: http://forum.world.st/Magritte-extension-tp4939046p4939547.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
On 22 Mar 2017, at 00:46, Ben Coman <btc@openInWorld.com> wrote:
On Wed, Mar 22, 2017 at 4:35 AM, DiegoLont <diego.lont@delware.nl> wrote:
It has been a while that I was really involved in developing on (QC)Magritte and doing stuff on the web ...
btw, what does the "QC" represent?
QC is a reference back to the company for who the software was originally written for: http://www.q-software-solutions.de/index.htm. The owner (Friedrich Dominicus) agreed that I was allowed to make the library part (QCMagritte) open source. Cheers, Diego
Magritte is nice but the amount of work is just too much for my taste. Simple forms are better handled with somethibg like Mold. And this especially when components interact with a ton of Js. Phil Le 22 mars 2017 19:53, "Diego Lont" <diego.lont@delware.nl> a écrit :
On 22 Mar 2017, at 00:46, Ben Coman <btc@openInWorld.com> wrote:
On Wed, Mar 22, 2017 at 4:35 AM, DiegoLont <diego.lont@delware.nl> wrote:
It has been a while that I was really involved in developing on (QC)Magritte and doing stuff on the web ...
btw, what does the "QC" represent?
QC is a reference back to the company for who the software was originally written for: http://www.q-software-solutions.de/index.htm. The owner (Friedrich Dominicus) agreed that I was allowed to make the library part (QCMagritte) open source.
Cheers, Diego
On 22 Mar 2017, at 20:36, phil@highoctane.be wrote:
Magritte is nice but the amount of work is just too much for my taste. Simple forms are better handled with somethibg like Mold.
And this especially when components interact with a ton of Js.
Then I want you to challenge you: try the QCMagritte tutorial. I took me 3 hours, including the time to make some improvements on the tutorial, and please tell me if you still believe it takes a ton of time to make something nice.
First of all I want to advertise QCMagritte: This framework is easy to use. It has a seaside like tutorial, that every developer should be able to follow without any significant problems and shows all significant features of both Magritte, Seaside and QCMagritte. Although it lacks documentation on the technical details of the framework, it has documentation included how to use the framework (as a developer).
Shame on me, advertising the tutorial of QCMagritte without checking it actually works. I fixed the bug that prevented me from starting the first page (rendering a keep alive) of the tutorial this morning, and started trying it out this evening. Along the way I found some typoâs and things that could be explained better, so I made some improvements to the tutorial along the road. I also noticed that some topics are not covered yet in this tutorial ⦠but since no one complained about the tutorial being buggy, not many people have tried the tutorial ?!?
On Thu, Mar 23, 2017 at 5:25 AM, Diego Lont <diego.lont@delware.nl> wrote:
First of all I want to advertise QCMagritte: This framework is easy to use. It has a seaside like tutorial, that every developer should be able to follow without any significant problems and shows all significant features of both Magritte, Seaside and QCMagritte. Although it lacks documentation on the technical details of the framework, it has documentation included how to use the framework (as a developer).
Shame on me, advertising the tutorial of QCMagritte without checking it actually works.
I fixed the bug that prevented me from starting the first page (rendering a keep alive) of the tutorial this morning, and started trying it out this evening. Along the way I found some typoâs and things that could be explained better, so I made some improvements to the tutorial along the road. I also noticed that some topics are not covered yet in this tutorial ⦠but since no one complained about the tutorial being buggy, not many people have tried the tutorial ?!?
Can you link the tutorial? cheers -ben
On 23 Mar 2017, at 04:27, Ben Coman <btc@openinworld.com> wrote:
On Thu, Mar 23, 2017 at 5:25 AM, Diego Lont <diego.lont@delware.nl> wrote:
First of all I want to advertise QCMagritte: This framework is easy to use. It has a seaside like tutorial, that every developer should be able to follow without any significant problems and shows all significant features of both Magritte, Seaside and QCMagritte. Although it lacks documentation on the technical details of the framework, it has documentation included how to use the framework (as a developer).
Shame on me, advertising the tutorial of QCMagritte without checking it actually works.
I fixed the bug that prevented me from starting the first page (rendering a keep alive) of the tutorial this morning, and started trying it out this evening. Along the way I found some typoâs and things that could be explained better, so I made some improvements to the tutorial along the road. I also noticed that some topics are not covered yet in this tutorial ⦠but since no one complained about the tutorial being buggy, not many people have tried the tutorial ?!?
Can you link the tutorial? cheers -ben
Maybe including the tutorial in a QCMagritte image was not very obvious ⦠QCMagritte can be found on smalltalk hub ( http://smalltalkhub.com/#!/~DiegoLont/QCMagritte/ ) and pharo CI ( https://ci.inria.fr/pharo-contribution/job/QCMagritte/ ). So download a fresh pharo image, open it and perform the following: Gofer new url: 'http://smalltalkhub.com/mc/DiegoLont/QCMagritte/main'; package: 'ConfigurationOfQCMagritte'; load. ((Smalltalk at: #ConfigurationOfQCMagritte) project version: #'development') load: #( 'All' ). (Smalltalk at: #ZnZincServerAdaptor) startOn: 8080 Doing this should give you a working QC Magritte tutorial hosted on your own pc. You can also download a pre build image from the pharo ci server. When you have an running image with QCMagritte: start a browser on http://localhost:8080/ and the tutorial should pop up.
participants (4)
-
Ben Coman -
Diego Lont -
DiegoLont
-
phil＠highoctane.be