You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(22) |
Jun
(10) |
Jul
(9) |
Aug
(4) |
Sep
(6) |
Oct
(1) |
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
(2) |
Feb
|
Mar
(8) |
Apr
(11) |
May
(1) |
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
(12) |
Nov
|
Dec
|
2005 |
Jan
(4) |
Feb
(2) |
Mar
(9) |
Apr
(20) |
May
(8) |
Jun
(4) |
Jul
(9) |
Aug
(25) |
Sep
(6) |
Oct
(1) |
Nov
(3) |
Dec
|
2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
(1) |
Jul
(4) |
Aug
(1) |
Sep
|
Oct
(2) |
Nov
|
Dec
|
2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(5) |
Jun
|
Jul
(18) |
Aug
(17) |
Sep
(19) |
Oct
(1) |
Nov
(3) |
Dec
|
From: Sergio V. S. <sv...@ig...> - 2005-11-09 11:13:25
|
Hi, some weeks ago we agreed that the name of the new Fisterra development will be Fisterra Garage instead the old codename Fisterra Repair. Nowadays there were still a lot of references to the old name. I changed those references, it could be still some, so please report any unchanged reference. My advice is to perform a complete checkout in order to avoid any problem. Bye. |
From: Javier F. <jfe...@ig...> - 2005-11-02 09:51:37
|
A new Fisterra BModule has been implemented to Fisterra ERP development framekork. This module, called as Migration, implements the data transfers between legacy information systems and the Fisterra operational database. You can examine the porject documentaiton to knonw more about this new module and the migration process implemented. Greetings, -- Javier Fernández García-Boente Ingeniero en Informática mailto:jfe...@ig... Igalia S.L. http://www.igalia.com Telf. +34 981 91 39 91 Fax. +34 981 91 39 49 |
From: Sergio V. S. <sv...@ig...> - 2005-10-11 17:21:16
|
Hi, I have just removed the dependency between the document and tax modules. I have removed the tax and taxable attributes of document line. These changes, of course, affect also both Fisterra Distribution and Fisterra Garage. Both of them have been updated according to the new data structure. The bmodules package current version is 2.1.2 Bye. |
From: D. P. <jd...@ig...> - 2005-09-21 15:51:57
|
Hi: Today I've uploaded some changes to the Fisterra project webpage. The main changes are the following: * Now external links are marked with a Earth logo. It let the user realize that the pointed link is to another web. * Changed the cryptic POS acronym by Point of Sale, linked to the Wikipedia. * In general, changing all the references to Fisterra 1.x to Fisterra Garage, to reflect the change of the legacy project. I added some clarifications in certain sections of the project web. * Rework of the Features section, with a better organization of the terms, adding articles for explaining what is a Fisterra Barnacle, and what is an Enterprise GNOME Barnacle. * Update of the roadmap. * Improved some descriptions of what Fisterra is. * More references and clarifications about fisterra-bmodules. As usual, you can access to the webpage in: http://www.fisterra.org If you have any suggestion about the contents, please let me know, or send a mail to this list. --=20 Jos=E9 Dapena Paz <jd...@ig...> Igalia, S.L. |
From: Sergio V. S. <sv...@ig...> - 2005-09-20 10:35:29
|
Hi, I have just released the new upstream version (2.1.3) of fisterra-base. The attribute "default_new" that was unused has been replaced by "listing". The new attribute is useful for specifying in the xml controllers file the concrete type of listing controller that should be instantiated by the f_control_listing_builder. You can download it from the HEAD of fisterra-base or with the tag fisterra-base-2_1_3 Bye. |
From: Sergio V. S. <sv...@ig...> - 2005-09-12 08:25:03
|
Hi, I think the name of the hostcode attribute of the database should not be hard coded, so I decided to add an attribute to the |hostcode| tag called |atr|. There you can specify the name of the attribute that holds the hostcode value in the database. For example, supose that the table |shop| stores the hostcode value on an attribute called |hc| then we can write <table name="shop" alias="sp" ....> <hostcode atr="hc"/> </table> and the join condition will be something like this .... AND sp.hc = hostcoded_read_with_f_parameter_manager Greetings. |
From: Sergio V. S. <sv...@ig...> - 2005-09-09 15:17:59
|
Hi, due to the fisterra-repair-server is now a shell script it is not possible to debug the server with gdb directly. If you use gdb from the command-line you can type libtool --mode=execute gdb but the emacs gdb mode does not like this command. I found a solution for going on debugging the server with the emacs gdb mode. First of all create a shell script with this code #!/bin/sh exec libtool --mode=execute gdb $* and place it in any directory of your $PATH environment variable. I called it wrapper. Go to the src/server directory and execute emacs there. Then when emacs asks for the gdb command (after C-x gdb) just type: wrapper fisterra-repair-server you will be able to run the nice gdb emacs mode. Bye. |
From: Sergio V. S. <sv...@ig...> - 2005-09-09 14:28:45
|
Hi, I have just added a new capability to the listing module located at fisterra basic modules. Sometimes we want to perform listings that dependes on the machine where the server is located. For example when I want to list the items of my own warehouse. We used to pass the hostcode of the server from the client as a hidden rule, but our policy is never trust the client so we had to achieve a better solution. We decided to add a new tag called |<hostcode/>| that will be placed in the listing source file inside a |<table>| tag into the from section. For example: <table name="warehouse" alias="war" join-cond="st.warehouse = war.code" left="yes"> <hostcode/> </table> The listing service will proceed as follows once the tag hostcode was detected: * recover the hostcode with |f_parameter_manager| * add a condition to the join condition built from this |<table>| tag. The condition follows this structure: [name_of_the_parent_tag].hostcode = hostcode (acquired in the first step) So the join condition will be: |(st.warehouse = war.code) and (war.hostcode = 1)| (supose the |f_parameter_manager| returned 1 as the value of the host code). Greetings. |
From: Javier F. <jfe...@ig...> - 2005-09-06 10:12:45
|
The project name has been changed to Fisterra-Garage, to describe vertical implementations for vehicle repairs business developed in this project.=20 There was a problem with the link defined in this web to the SourceForge dowloads web. This link downloaded directly the previous version (1.5).=20 The main release published on SourceForge dowlonad page is 1.6, see this page for more details about Fisterra stable releases. You can dowload the last version of Fisterra-Garage ERP applications at : http://sourceforge.net/project/showfiles.php?group_id=3D78897&package_id=3D= 80133&release_id=3D352666 Greetings, --=20 Javier Fern=E1ndez Garc=EDa-Boente Ingeniero en Inform=E1tica =20 mailto:jfe...@ig... =20 Igalia S.L. http://www.igalia.com Telf. +34 981 91 39 91 =20 Fax. +34 981 91 39 49 |
From: Carlos <csa...@ig...> - 2005-08-31 18:47:32
|
Hi folks, We've added a generic form controller (FControlForm) and a generic form builder (FControlFormBuiler). It can be used for common i/o detail windows, such as insert or update items. How is a form window implemented using this controller? Simple, we have to configure concrete parameters for our controller instance with a 'FClientForm structure. Next are the required parameters: typedef struct _FClientForm { gchar *f_client_form_name; gchar *f_client_form_window_name; FCommonFacade *(*f_client_form_facade_new)(void); GtkWidget *(*f_client_form_widget_new)(void); FModel *(*f_client_form_model_new)(void); gboolean (*f_client_form_set_initial_data)(FCommonFacade *facade, FModel *model); gboolean (*f_client_form_set_detail_data)(FCommonFacade *facade, guint64 code, FModel *model); gboolean (*f_client_form_save_model)(FCommonFacade *facade, FModel *model); } FClientForm; We can specify any facade, widget and model function for our controller. When we add the controller into controllers definition xml file, we'll reference the "f_client_form_name" from a new "form_name" entry. It's thus because main controller saves an object to mapping the form controller definition with this string as key. <controller name=3D"f_control_form_item" builder=3D"FControlFormBuilder" menu_option=3D"Item Detail" action_name=3D"ItemDetail" form_name=3D"item_detail_form" embedded=3D"false"/> Now, we have to create glade, widget, model and facade functions :). An example of use is item_detail_form (with f_widget_item_detail and f_model_item_detail) of fisterra-repair. For further information, view the section 'Form window implementation' of the 'fisterra-base' doc. Greetings. --=20 Carlos Sanmart=EDn Dom=EDnguez <csa...@ig...> Telf: +34 981 91 39 91 Igalia, S.L. http://www.igalia.com |
From: Javier F. <jfe...@ig...> - 2005-08-29 19:17:06
|
On Mon, Aug 29, 2005 at 09:07:33PM +0200, Javier Fernandez wrote: > New release Fisterra-1.6 is now available. New features and fixed bugs > are developed for the vertical implementation for vehicle repair > business, based on Fisterra1 development framework. > You can download it from SourceForge (http://sourceforge.net) -- Javier Fernández García-Boente Ingeniero en Informática mailto:jfe...@ig... Igalia S.L. http://www.igalia.com Telf. +34 981 91 39 91 Fax. +34 981 91 39 49 |
From: Javier F. <jfe...@ig...> - 2005-08-29 19:07:49
|
New release Fisterra-1.6 is now available. New features and fixed bugs are developed for the vertical implementation for vehicle repair business, based on Fisterra1 development framework. This version has been updated to fix bugs detected during the first two years of application running on various real business environments. Some new features has been developed too : - Clients has a default payment method, which it will be used in invoicing process. - Some database queries has been reviewed to optimize these critical search operations, such invoice and IVA listings. - The envelopes printing has been enable for multiple clients. A client listing can be used to print all envelopes with the default address. - The repairs listing has been modified to include a new column, to show the accident reference, associated to the repair work. - A new field has been added to manages provider selection. This filed is the AUTOVER code. This code is used by the AUTOVER provider, which is a very important provider for the most of business on which Fisterra1 is implemented. - New template printing has been designed, to adapt them to the template models of insurance companies. - The invoices interchange protocol implemented on Fisterra1 application has been modified to automate the sending process via mail. The installation process has been enhanced to make it more easy to the user. The dpkg installation use a dialog based configuration to assign the enterprise and shop parameters, configuring and install the database, dump the initial data required to run the application, and other configuration parameters and files, such logs and replication directories. This Fisterra-1.6 package has been compiled for Sarge Debian GNU/Linux distribution. -- Javier Fernández García-Boente Ingeniero en Informá¡tica mailto:jfe...@ig... Igalia S.L. http://www.igalia.com Telf. +34 981 91 39 91 Fax. +34 981 91 39 49 |
From: Alejandro G. C. <ac...@ig...> - 2005-08-25 12:15:24
|
Hi, we have uploaded new modules to fisterra-bmodules and now distribution depends on them, so if you download the HEAD of distribution you must download also and compile/install the HEAD of fisterra-bmodules and fisterra-base. The new modules are: - Actor has been modified, we have added accountabilities, contacts, address, etc. - Calendar, representing calendars inside fisterra - Tax, class structure to store taxs - Document, data and business code of the fisterra workflow. You'll find more information about this modules on its documentation directory, they all have at least a class diagram with the data structure. We will try to add more documentation soon. We have also added a new API function on the EGBS in order to define DEFERRED transactions, because we are allowing reciprocal dependent classes. Regards. -- Alejandro Garcia Castro mailto: ac...@ig... http://www.igalia.com |
From: D. P. <jd...@ig...> - 2005-08-24 12:06:58
|
El mi=E9, 24-08-2005 a las 13:40 +0200, Javier Fernandez escribi=F3: > El lun, 22-08-2005 a las 10:50 +0200, Wolfgang Keller escribi=F3: >=20 > > Well, Python is really fine, due to its "pseudo-code"-lookalike > > nature. > >=20 > > And if the original Gnome developer team had concentrated on > > completing the Corba services in GNOME to turn it into something close > > to a full reference implementation of Corba, then there would be > > everything a "non-professional" developer could dream of imho. Because > > with such a complete infrastructure, all you have to do is implement > > the application ("business") logic, and that's easy in Python. >=20 > I think python is a very good languaje to perform fast developemt, > including if developers are not professional. But im disagree when you > says that experts can use pytoh to program business logic. I think that > this is not a common situation; the business logic use to be a very > complex program task, and u doubt if expertts are able to make an > acceptable code. I think the huge complexity of business logic is enough. A friendlier language should be a way to help to implement this kind of tasks, without worrying about some things which are not related to business. Python is a good language for this, because it enables you to target your efforts in bussiness logic, forgetting a lot of issues about implementation (pointers and memory management, compilation environment, etc). And, in the top of all these things, the loose of efficiency should be minimal, because you are accessing to a relational database, which should be a slower task for the system. For me, enabling the user to use development environments with lighter or null compilation environments would be a big improvement in Fisterra SDK. --=20 Jos=E9 Dapena Paz Ingeniero en Inform=E1tica Telf: +34 981 91 39 91 ext. 15 Fax: +34 981 91 39 49 mailto:jd...@ig... IGALIA, S.L. http://www.igalia.com |
From: Javier F. <jfe...@ig...> - 2005-08-24 11:40:53
|
El lun, 22-08-2005 a las 10:50 +0200, Wolfgang Keller escribi=F3: > Well, Python is really fine, due to its "pseudo-code"-lookalike > nature. >=20 > And if the original Gnome developer team had concentrated on > completing the Corba services in GNOME to turn it into something close > to a full reference implementation of Corba, then there would be > everything a "non-professional" developer could dream of imho. Because > with such a complete infrastructure, all you have to do is implement > the application ("business") logic, and that's easy in Python. I think python is a very good languaje to perform fast developemt, including if developers are not professional. But im disagree when you says that experts can use pytoh to program business logic. I think that this is not a common situation; the business logic use to be a very complex program task, and u doubt if expertts are able to make an acceptable code. --=20 Javier Fern=E1ndez Garc=EDa-Boente Ingeniero en Inform=E1tica =20 mailto:jfe...@ig... =20 Igalia S.L. http://www.igalia.com Telf. +34 981 91 39 91 =20 Fax. +34 981 91 39 49 |
From: Wolfgang K. <wol...@gm...> - 2005-08-22 08:51:01
|
Hallo, > On Fri, Aug 19, 2005 at 09:48:19AM +0200, Wolfgang Keller wrote: >> Hello, >> >> [...] >> >> > As a complementary vision we are devoting more effort on the code >> > reuse of concrete business analysis on a multiuser environment, this >> > is our actual aim. >> >> Well, that comes on top of the infrastructure. And it should use tools >> that are usable by domain experts, who are not necessarily developers. >> > This is very important, my point of view about this topic is that the > experts may known the use of tools like: umbrello and docbook. Well, Python is really fine, due to its "pseudo-code"-lookalike nature. And if the original Gnome developer team had concentrated on completing the Corba services in GNOME to turn it into something close to a full reference implementation of Corba, then there would be everything a "non-professional" developer could dream of imho. Because with such a complete infrastructure, all you have to do is implement the application ("business") logic, and that's easy in Python. I would bet that Mono will never provide something comparable to such a full Corba infrastructure. Apart from its ties with Microsoft, obviously. Sincerely, Wolfgang Keller -- P.S.: My From-address is correct |
From: Alejandro G. C. <ac...@ig...> - 2005-08-19 12:15:57
|
fisterra-bmodules is a package with some basic modules of fisterra, their main feature and the reason they are not in fisterra-base is because they are business data dependent. The general business problems solved in the fisterra projects will be added to this repository in order to be reused on other projects. The modules that we have right now are: - actor, the business actor analysis pattern, not still a good solution - auth, the authorization system - listing, module used to easily create data lists, avoiding object oriented management We have used this version number because this code is just a refactorization of code, and for release management simplicity. Changes since 2.1.0 ------------------- - Added the listing module You can download the source code from the igalia cvs repository as usual: http://community.igalia.com/twiki/bin/view/Fisterra/ProjectCVS You can find more information about the project on the webpage: http://www.igalia.com Regards -- Alejandro Garcia Castro mailto: ac...@ig... http://www.igalia.com |
From: Alejandro G. C. <ac...@ig...> - 2005-08-19 12:15:57
|
fisterra-base is the basic fisterra library, it includes the support code of the fisterra environment: code_generation, base objects, database access, interface structure, etc. This release is a unstable minor release of the library, it contains big changes from the last stable release. It is not compatible with the last stable release. We have created a new package fisterra-bmodules, with some parts of base and the linked code that is business dependent. Changes since 2.1.0 ------------------- - No class IDs required for the data definition xml - New inheritation system for the data definition xml, ancestor attribute - XInclude supported on the data definitions xml - Added module name definition to the data definitions xml - Removed the listing module code, it has been moved to fisterra-bmodules. - Removed the authentication system, it has been moved to fisterra-bmodules. You can download the source code from the igalia cvs repository as usual: http://community.igalia.com/twiki/bin/view/Fisterra/ProjectCVS You can find more information about the project on the webpage: http://www.igalia.com Regards -- Alejandro Garcia Castro mailto: ac...@ig... http://www.igalia.com |
From: Alejandro G. C. <ac...@ig...> - 2005-08-19 12:15:57
|
fisterra-distribution is a sectorial implementation above the fisterra environmente oriented to the retail business, with beta POS functionality. This release uses the new fisterra-bmodules package, it imports and uses the actor, auth and listing modules. Changes since 2.0.0 ------------------- - Added the actor, listing and auth bmodules dependency - Removed the order and order lines class - debian/rules: Added --enable-gtk-doc to configure - Added dependencies with * librecode0 * barcode * libmagick6 You can download the source code from the igalia cvs repository as usual: http://community.igalia.com/twiki/bin/view/Fisterra/ProjectCVS You can find more information about the project on the webpage: http://www.igalia.com Regards -- Alejandro Garcia Castro mailto: ac...@ig... http://www.igalia.com |
From: Alejandro G. C. <ac...@ig...> - 2005-08-19 09:14:34
|
On Fri, Aug 19, 2005 at 09:48:19AM +0200, Wolfgang Keller wrote: > Hello, > > [...] > > > As a complementary vision we are devoting more effort on the code > > reuse of concrete business analysis on a multiuser environment, this > > is our actual aim. > > Well, that comes on top of the infrastructure. And it should use tools > that are usable by domain experts, who are not necessarily developers. > This is very important, my point of view about this topic is that the experts may known the use of tools like: umbrello and docbook. The development environment must be able to implement that specification of the expert as detailed as posible and must be also reusable in all the projects implemented, meaning easily included and extended. The latter feature when we talk about a module implementing a solution proposed for example in Martin Fowler's "Analysis Patterns: Reusable Object Models", that are data dependent, I think is the most important for the environment, we increase the speed of the development reusing the parts of these good solutions: widgets, communications, logic or storage. We hope our current module definition will allow us this kind of develpment. Greetings. -- Alejandro Garcia Castro mailto: ac...@ig... http://www.igalia.com |
From: Wolfgang K. <wol...@gm...> - 2005-08-19 07:48:30
|
Hello, > Well, some people are interested, but our community is still smaller > than we would like ;-). Unfortunately the original GNOME developers didn't seem to see the lack of server-side infrastructure or didn't want to work on it and went somewhere else... > AFAIK there are some other projects using glib-gobject on the server > side, two examples that you can browse are evolution-data-server and > aspl-fact. Using GNOME technology there are some projects that has > to do with business applications, for example: pygestor, tinyerp or > gctb. I already know about TinyERP. Maybe it would be possible to split-off the application server and workflow engine into seperate projects that would then be available for other projects as well. That would already give two essential components. Others would be security, transactions... > Currently glom or gazpacho are also trying to implement a fast > development environment of the this kind of applications. In fact there seem to be plenty of individual projects especially in spanish-speaking countries that try to do more or less the same thing. But as long as they don't get their resources together and co-ordinate their effort to integrate common basic infrastructure components into something like a "GNOME enterprise edition"... > As a complementary vision we are devoting more effort on the code > reuse of concrete business analysis on a multiuser environment, this > is our actual aim. Well, that comes on top of the infrastructure. And it should use tools that are usable by domain experts, who are not necessarily developers. Sincerely, Wolfgang Keller -- P.S.: My From-address is correct |
From: Alejandro G. C. <ac...@ig...> - 2005-08-18 19:47:44
|
On Thu, Aug 18, 2005 at 11:29:42AM +0200, Wolfgang Keller wrote: > Hello, > > a different question that arose when reading the Fisterra > documentation: > > Did anyone pick up your proposal for specifying/implementing a > server-side equivalent of the GNOME desktop environment for > server-side "enterprise" applications including services such as e.g. > security, persistence, transactions etc.? Or could you find anyone > else already working on such a project? > Well, some people are interested, but our community is still smaller than we would like ;-). AFAIK there are some other projects using glib-gobject on the server side, two examples that you can browse are evolution-data-server and aspl-fact. Using GNOME technology there are some projects that has to do with business applications, for example: pygestor, tinyerp or gctb. Currently glom or gazpacho are also trying to implement a fast development environment of the this kind of applications. As a complementary vision we are devoting more effort on the code reuse of concrete business analysis on a multiuser environment, this is our actual aim. I hope we can sum efforts as soon as posible wiht these related projects and others because is the main reason we are using GNOME technologies. Greetings. -- Alejandro Garcia Castro mailto: ac...@ig... http://www.igalia.com |
From: Wolfgang K. <wol...@gm...> - 2005-08-18 16:36:52
|
Hello, a different question that arose when reading the Fisterra documentation: Did anyone pick up your proposal for specifying/implementing a server-side equivalent of the GNOME desktop environment for server-side "enterprise" applications including services such as e.g. security, persistence, transactions etc.? Or could you find anyone else already working on such a project? TIA, Sincerely, Wolfgang Keller -- P.S.: My From-address is correct |
From: Alejandro G. C. <ac...@ig...> - 2005-08-17 17:28:22
|
On Wed, Aug 17, 2005 at 06:43:53PM +0200, Wolfgang Keller wrote: > Hallo, > > > None, it is a pity but we have not time to work on this feature :-/. > > Maybe you would have more time if you had implemented only the common > base infrastructure for Fisterra in C(++) and all the upper-level > "business logic" in Python from the start... *duck* :-) Because > Python is really pretty readable/usable for non-developers, so > domain specialists could help directly with the implementation. > Maybe you are right, that's why we are interested on this feature indeed. Until now we were devoting our resources to other basic issues, the business logic reuse system it is going to be pretty interesting, I'll like to see it python-integrated. Anyway, I hope we could know if you are right in the future ;-), thank you for your advise. Best Regards. -- Alejandro Garcia Castro mailto: ac...@ig... http://www.igalia.com |
From: Wolfgang K. <wol...@gm...> - 2005-08-17 16:44:14
|
Hallo, > None, it is a pity but we have not time to work on this feature :-/. Maybe you would have more time if you had implemented only the common base infrastructure for Fisterra in C(++) and all the upper-level "business logic" in Python from the start... *duck* :-) Because Python is really pretty readable/usable for non-developers, so domain specialists could help directly with the implementation. Sincerely, Wolfgang Keller -- P.S.: My From-address is correct |