Re: [Dataperf] HTML

[Gary_Gabriel]

Brian Hancock wrote: Hi Brian, Glad to hear from you and that you find the articles interesting. Fortunately I figured out where the problem was with the Xslt transform. It was the typical problem when introducing new tools and programming at the same time. I misunderstood the logic of the Xalan processor use. After getting it right everything worked like a charm- not meaning that I am competent only that I got over the introductory hurdle. I had used DP programming logic and your explanations to write a number of templates. But none of them transformed. It was disappointing because I thought I understood the syntax, and using prior DP experience would progress me. Now that they are working I am convinced that writing the templates is very similar to building a panel and populating it with fields. It fits very well with the DP logic and architecture. I now have a basic set of templates and continue more relaxed with web enabling DP. I am convinced that the future of Xslt and Xml will produce the layered architecture you described in your e-mail. I will employ it to build distributed (process) databases. Thanks  for your other tips, I will add them to the consideration, planning and implementation. My thoughts for a simple panel browsers were based on using the STE-MGR.com and STE-BASE applications to build the structure into forms, with a library or _javascript_ and AJAX to provide the interactivity.  I have recently started using Flex, and I have thought it might be even easier to use this as a form designer. With I would envisage a report in the STE-BASE which outputs a Flex MXML file defining the “panel” The balance of the application could be a standard set of  components and classes which add search, lookup, new record, save, edit delete functions whih would then be used by a set of libraries on the server to communicate with DP. This is exactly where I would like to see DP positioned and what I need to produce the forms. Using your example, DP provides a simple UI in the browser where the user inputs (xml) data. DP maintains the data and manipulates it. According to my example it resides in the browser/ e-mail so that the user has a unified UI. It also allows the user to edit it and add to the db. Then DP outputs the data in the needed form (xml) where it then formats into Html, doc ..... Some of these forms store in a local web server (in the browser). Using web standards and technology they manipulate in a way very similar to what we are used to with DP. For example go through Ralph's  book on DP and use the chapter titles: for each one of these chapters- Fields, Lookups, Indexes, Links, Reports, Report Variables, Formulas, Iteration Control ... there is a web server database analogy. Not only is this book useful as a standard work on databases; but it (would) enable the distributed database architecture described by you yesterday next to the DP functionality. Just to add a personal comment; I am open to any environment that would provide a (modern) UI for the layered db architecture. I briefly addressed my reservations yesterday about mainline software manufacturers. I have little experience with Adobe but use Photoshop and Adobe is one of the few manufacturers that still knows how to produce quality. But I immersed myself in the Open Source world and I enjoy the advantages of lean, targeted software that installs op and hardware independently. It also enables an op independent profile installation. I took all data out of the e-mail and browser profiles putting it into a network drive and I can move to any computer install the application, load my profiles and address flash drives to run my applications. Similarly downloading the profiles moves the specific profile application without subjecting the data to security risks. And this software proves to run stable and install clean. Your articles on Scribd are interesting. Just to clarify, are you using IM to automate contact with people, to send say projects managers automated to-do messages based on their project schedule?  I have not ever thought of using IM in an automated manner. First to produce the project manager to-dos right in the IM at the point of entry. Then to share the to-dos with the team. Then to automate the processes based on the to-dos. Lastly facilitate the project management documentation and distribution. Use the benefit of the knowledge and experience stored in the team project to produce knowledge bases for support. My experience with Contact, Lead and Project Management (PM) and Web Research shows that: 1) Duplicated contact entry creates a great deal of unnecessary effort. It also creates user problems when he tries to remember how and where to enter data. Simply use the contact info as it comes without replicating it in a db. How do you do that? Use the document encasing the contact data: now a days e-mail and Internet. Most contacts provide a unique index with the e-mail address or a URL. The user later extends the data content by adding documents. 2) The last generation of my db lost flexibility because of replicating indexes. It became very difficult to make significant improvements because the number of indexes increased. I analyzed the index multiplicity. I now have a mathematical theorem and proof which is being finished to publish that proves one index of two dimensions/ variables suffices to uniquely describe an entire space. Similar to the space of your layered dbs. It requires two independent dimensions or variables. After a lot of experimenting in the areas mentioned above two dimensions proved to be activities or projects and information resources. First the definition and a simple proof. List the activities or projects started each year. This is the set of activities. List the information domains used to action these activities these are the Information Resources. Using my example the Information Resources are: Business Administration. Application Technology including pc's, software, networking, messaging, internet e-mail, system administration. Then go to Language, Physics, Math, Philosophy ... A simple proof of independency: 1) how can you action the projects without the Information Resources? 2) What good are the Information Resources without the projects? Project Management matches the project with the (most) appropriate Information Resource. This example illustrates that the projects and Information Resources are independent of another. It suggests a proof that you can later read.  This is the story of spiral growth. Look at the circle it combines two dimensions (x,y) and combines them in varying quantities as it moves around the perimeter. This circular movement around the circle defines the message cycle See  Streamlining Sales Cycle Management with Internet Messaging >>> for a definition and examples of the message cycle. Or On the Way I met Internet Messaging. It took me .... >>>  for more background information. It applies equally to Sales Cycle Management, Strategic Business Development .... Now my dbs use one index and an incrementation to index the entire application to enable rapid deployment of changes and ease and efficiency of data entry. I know that this is a controversial design issue. IM builds the common point of entry of the incoming contact (documents). It ques the contact and attaches forms generated by a layered db to control the further Lead and Project Management or processing. It easily includes the Web Research using the similarities between Project Management and Web Research. This point of entry begins the automation and processing continued by forms within the IM. They communicate with other db's and processes via the layers described by you. After building a streamlined and automated Project Management it extends to specialize for further applications. I built the Sales Cycle Management and Strategic Business Development on top of the Project Management. The extension includes adding forms that store the data. For the data objects, transactions and views see a member of the Scribd Hotlist:  Quick Reference to Sales Cycle Management Objects to drive Strategic Business Development Aggregates  >>>   or Sales Cycle Lead and Contact Data Objects, Transactions and Views  >>>    For forms see: Sales Consulting Templates for use in a Team Knowledge Base  >>> You will see that the forms consider xml structure and schema. As I become more experienced and knowledgeable, they will better conform. The last forms make it obvious that DP panels are not useful for documenting concepts or relationships. The Sales Consulting Templates require a page view and editing to make use of the field relationships. This was originally implemented in DP but these panels were replaced. Summary: if you start a project to produce the proposed UI It would handle the IM and PM. Then specialize the PM to handle the individual application. DP provides a core to store, edit and manipulate the layers of IM, PM and application. Currently my Firefox and Thunderbird profiles fulfill my test IM/ PM requirements. The e-mail client Thunderbird functions as a database of message documents. See Using Common Ground to shorten Team Contact, Lead and Project Management >>>  for an overview of the articles treating the basics, the theory and strategy and the configuration of IM with Mozilla.. Extend the IM layer to producing knowledge bases and you produce them on-line as you develop.  For an overview of driving the application using IM and producing support systems to benefit the user see  Store and Process Team Knowledge and Experience to qualify Support >>>    Thanks for your useful thoughts and inputs. - Gary

_______________________________________________
Dataperf mailing list
Dataperf@dataperfect.nl
http://lists.dataperfect.nl/mailman/listinfo/dataperf