developer toolbox

(16:16:53) vsasa: vidiš pamentno sam uradio pa sam stavio sve to u ove dvije odvojene baze
(16:17:00) vsasa: da nemoramo ići na 5 tabela
(16:17:01) hernad: radi li ti ping gitorious.bring.out.ba
(16:18:43) hernad: izgleda da je to core harbour funkcija
(16:19:13) hernad: http://gitorious.bring.out.ba/harbour/harbour/trees/master/harbour
(16:19:24) hernad: i onda imaš stablo gir repozitorija harbour-a
(16:20:48) hernad: evo ga
(16:21:58) hernad: http://gitorious.bring.out.ba/harbour/harbour/blobs/master/harbour/contrib/xhb/txml.prg
(16:22:20) vsasa: ja tome ne mogu pristupiti ? vpn ?
(16:25:59) hernad: samo je u lan-u dostupno trenutno

bringout@nmraka-2:~/devel/git/upstream/harbour/harbour/contrib/xhb/hbxml.c

* This source file contains a modified version of MXML (Mini XML)
* library, developed by Giancarlo Niccolai. MXML is released under
* LGPL license; this modified version (called HBXML) is released under
* GPL with HARBOUR exception. HBXML license does not extends into
* MXML; HBXML and any modification to HBXML is to be considered as
* a part of Harbour or xHarbour projects, as it is modified to
* be specifically working in the context of the compiler's RTL.

evo to je to

http://www.minixml.org/

harbour je napravio bindings prema ovoj biblioteci

http://www.minixml.org/documentation.php/basics.html

You can create and update XML documents in memory using the various mxmlNew functions. The following code will create the XML document described in the previous section:

    mxml_node_t *xml;    /* <?xml ... ?> */
    mxml_node_t *data;   /* <data> */
    mxml_node_t *node;   /* <node> */
    mxml_node_t *group;  /* <group> */

    xml = mxmlNewXML("1.0");

    data = mxmlNewElement(xml, "data");

        node = mxmlNewElement(data, "node");
        mxmlNewText(node, 0, "val1");
        node = mxmlNewElement(data, "node");
        mxmlNewText(node, 0, "val2");
        node = mxmlNewElement(data, "node");
        mxmlNewText(node, 0, "val3");

        group = mxmlNewElement(data, "group");

            node = mxmlNewElement(group, "node");
            mxmlNewText(node, 0, "val4");
            node = mxmlNewElement(group, "node");
            mxmlNewText(node, 0, "val5");
            node = mxmlNewElement(group, "node");
            mxmlNewText(node, 0, "val6");

        node = mxmlNewElement(data, "node");
        mxmlNewText(node, 0, "val7");
        node = mxmlNewElement(data, "node");
        mxmlNewText(node, 0, "val8");

We start by creating the node common to all XML files using the mxmlNewXML function:

    xml = mxmlNewXML("1.0");

We then create the <data> node used for this document using the mxmlNewElement function. The first argument specifies the parent node (xml) while the second specifies the element name (data):

    data = mxmlNewElement(xml, "data");

Each <node>...</node> in the file is created using the mxmlNewElement and mxmlNewText functions. The first argument of mxmlNewText specifies the parent node (node). The second argument specifies whether whitespace appears before the text - 0 or false in this case. The last argument specifies the actual text to add:

    node = mxmlNewElement(data, "node");
    mxmlNewText(node, 0, "val1");

The resulting in-memory XML document can then be saved or processed just like one loaded from disk or a string.

HarbourEnvVars

ovaj ticket #17239 govori o mingw build-u

http://aruiz.typepad.com/siliconisland/2006/08/clipem_my_own_c.html

function main()
xTag := TXMLNODE
xTag:SetAttribute("attr", "value")

xAnotherTag := TXMLNODE(0, "childNode")

xTag:AddBelow(xAnotherTag)

?xTag:ToString(1)
        WAIT
return ( nil )

da potražim taj mini xml - mxml

bringout@nmraka-2:~/devel/git$ aptitude search mxml

p   libmxml-dev                     - small XML parsing library (development)   
p   libmxml1                        - small XML parsing library (runtime)

napravio novi deb, pa onda ga instalirao

da vidim da li postoji u libxhb TXMLNODE

bringout@nmraka-2:~/devel/git$ nm /usr/lib/harbour/libxhb.a | grep -i "XMLNODE"

00000000000002e0 T HB_FUN_TXMLNODE
0000000000000220 t HB_FUN_TXMLNODE_DEPTH
0000000000000260 t HB_FUN_TXMLNODE_NEW
0000000000000240 t HB_FUN_TXMLNODE_NEXTINTREE
0000000000000200 t HB_FUN_TXMLNODE_PATH

hm nisam ovi uspio skontati, da mi se ovaj xml podrška sviđa - ne sviđa.

Problem je što nikakvih primjera nema.

skino ovaj "xhgtk source"http://sourceforge.net/project/downloading.php?group_id=123078&filename=xhgtk20081217.zip da vidim da slučajno preko gtk nisu podržane xml funkcije - nisu.

a gledaj ruby-ja, on ima pure ruby XML library "rexml"

http://www.ruby-doc.org/stdlib/libdoc/rexml/rdoc/index.html

http://thestewscope.wordpress.com/2007/12/18/ruby-and-xml-schema/

znači xsd shema služi za validaciju generisanog xml-a.

xsd je struktura koja se očekuje od generisanog xml fajla.

U gornjim postovima se govori da REXML takav feature nema builtin ?

http://rubyforge.org/projects/libxml/

evo ruby binding-a za libxml2 gnome-ov koji sam na početku u chatu pominjao

libxml-ruby¶

http://libxml.rubyforge.org/

The Libxml-Ruby project provides Ruby language bindings for the GNOME Libxml2 XML toolkit. It is free software, released under the MIT License.

Libxml-ruby's primary advantage over REXML is performance - if speed is your need, these are good libraries to consider, as demonstrated by the informal benchmark below.

...

Often times you’ll need to validate data before processing it. For example, if you accept user generated content submitted over the Web, you’ll want to verify that it does not contain malicious code such as embedded scripts. This can be done using libxml’s powerful set of validators:

• DTDs (LibXML::XML::Dtd)
• Relax Schemas (LibXML::XML::RelaxNG)
• XML Schema (LibXML::XML::Schema)

? je li ovo zadnje xsd schema ?

http://www.mail-archive.com/xml@gnome.org/msg03517.html

Re: [xml] libxml2 XML Schema validation limitation

Daniel Veillard
Wed, 11 Oct 2006 12:09:28 -0700

On Wed, Oct 11, 2006 at 12:01:01PM -0700, Allison Bloodworth wrote:

It would REALLY help me if anyone could tell me when support for xs:redefine
might be added to libxml2's schema validation.

The person (Kasimier) who had done most of the Schemas specific parts
of the XSD implementation lost his job, and asked here for support. I guess
he is still looking for employment ...
If you want you can go read that spec and provide the missing bits for
the implementation.

Daniel

E sad ne znam da li je ovo out-of-date informacija (2006 godina), ali se ovdje govori da je implementacija xsd validacije nepotpuna

xjparse

The xjparse tool is a simple command-line wrapper for the Xerces XML Schema validator. It accepts several options, notably one which specifies the set of schemas to be used during validation.

http://xerces.apache.org/xerces2-j/

Welcome to the future! Xerces2 is the next generation of high performance, fully compliant XML parsers in the Apache Xerces family. This new version of Xerces introduces the Xerces Native Interface (XNI), a complete framework for building parser components and configurations that is extremely modular and easy to program.

The Apache Xerces2 parser is the reference implementation of XNI but other parser components, configurations, and parsers can be written using the Xerces Native Interface. For complete design and implementation documents, refer to the XNI Manual.

Xerces2 is a fully conforming XML Schema processor. For more information, refer to the XML Schema page.

i dođosmo do w3c specifikacije xml scheme http://www.w3.org/TR/xmlschema-0/

bringout@nmraka-2:~$ sudo gem install libxml-ruby

Building native extensions.  This could take a while...

u libxml-ruby našao test/* pa tu ima svega

evo đona

/var/lib/gems/1.8/gems/libxml-ruby-1.1.3/test/tc_schema.rb

require 'xml'
require 'test/unit'

class TestSchema < Test::Unit::TestCase
  def setup
    file = File.join(File.dirname(__FILE__), 'model/shiporder.xml')
    @doc = XML::Document.file(file)
  end

  def teardown
    @doc = nil
  end

  def schema
    document = XML::Document.file(File.join(File.dirname(__FILE__), 'model/shiporder.xsd'))
    schema = XML::Schema.document(document)
  end

  def test_from_doc
    assert_instance_of(XML::Schema, schema)
  end

  def test_valid
    assert(@doc.validate_schema(schema))
  end

  def test_invalid
    new_node = XML::Node.new('invalid', 'this will mess up validation')
    @doc.root.child_add(new_node)

    error = assert_raise(XML::Error) do
      @doc.validate_schema(schema)
    end

    assert_not_nil(error)
    assert_kind_of(XML::Error, error)
    assert(error.message.match(/Error: Element 'invalid': This element is not expected. Expected is \( item \)/))
    assert_equal(XML::Error::SCHEMASV, error.domain)
    assert_equal(XML::Error::SCHEMAV_ELEMENT_CONTENT, error.code)
    assert_equal(XML::Error::ERROR, error.level)
    assert(error.file.match(/shiporder.xml/))
    assert_nil(error.line)
    assert_nil(error.str1)
    assert_nil(error.str2)
    assert_nil(error.str3)
    assert_equal(0, error.int1)
    assert_equal(0, error.int2)
    assert_not_nil(error.node)
    assert_equal('invalid', error.node.name)
  end
end

i evo naša validacija radi

ruby test_xsd_1.rb

require 'rubygems'
require 'xml'

x_name = 'specif_pke.xml'
x_document = XML::Document.file(x_name)

s_document = XML::Document.file('specif_pke.xsd')
schema = XML::Schema.document(s_document)

new_node = XML::Node.new('invalid', 'this will napraviti error kod validacije')

#dodaj node
x_document.root.child_add(new_node)

x_document.validate_schema(schema)

Node#child_add is deprecated.  Use Node#<< instead.
Error: Element 'invalid': This element is not expected. Expected is ( {urn:SpecifikacijaZahtjevaZaIzdavanjePorezneKartice_V1_0.xsd}Obrazac1001 )..
test_xsd_1.rb:17:in `validate_schema': Error: Element 'invalid': This element is not expected. Expected is ( {urn:SpecifikacijaZahtjevaZaIzdavanjePorezneKartice_V1_0.xsd}Obrazac1001 ).. (LibXML::XML::Error)
    from test_xsd_1.rb:17

ako komentarišem dodavanje gornjeg noda (koji izaziva error), nema nikakvog report-a.

ako dodam:

puts x_document.to_s prije validacije, vidjeću sadržaj xml-a

.... kraj ...
        <Dio8IzjavaPoreznogObveznika>
            <VaziOd>1967-08-13</VaziOd>
        </Dio8IzjavaPoreznogObveznika>
    </Obrazac1001>
<invalid>this will napraviti error kod validacije</invalid></SpecifikacijaZahtjevaZaIzdavanjePorezneKartice>

Vidimo da je danu se ugnjezdila "<invalid>"

Dobro šta je zaključak: zaključak je da sa libxml2 sigurno možemo napraviti naš dokument, a evo validaciju smo sada vidjeli da funkcioniše.

Harbour je skroz pogrešan odabir. Bakćati se sa slabo dokumentovanom mxml nije korisno.

libxml2 je masovno korištena library. Sama činjenica da je gnome koristi je dovoljna.

"libxml2:"http://xmlsoft.org/¶

Libxml2 is the XML C parser and toolkit developed for the Gnome project (but usable outside of the Gnome platform), it is free software available under the MIT License. XML itself is a metalanguage to design markup languages, i.e. text language where semantic and structure are added to the content using extra "markup" information enclosed between angle brackets. HTML is the most well-known markup language. Though the library is written in C a variety of language bindings make it available in other environments.

Naravno mogli bi mi uzeti pa napraviti binding za harbour.

Fino odemo kupimo negdje droge ... napušimo se pa gdje stignemo ...

šalim se naravno :)

Što se pouzdanosti tiče:

In most cases libxml2 tries to implement the specifications in a relatively strictly compliant way. As of release 2.4.16, libxml2 passed all 1800+ tests from the OASIS XML Tests Suite.

ja sam se pitao da li će ovako parcijalan xml biti validiran kako treba ?

neće - žikne me u startu da stvar ne valja.

rezime¶

1. libxml-ruby radi ko čvoka
2. ruby je intuitivan, i bez problema sam uz rdoc libxml-ruby pohvatao način kako da kreiram xml
3. xsd validacija radi
4. poredak node-ova je bitan, što me je pravo začudilo

1. most između LD-PKE podataka i ruby aplikacije
2. konverzije polja iz clipper-a u odgovarajući xml format.
   1. Međutim treba dobro pogledati: libxml-ruby sigurno zna odgovarajuće ruby tipove pretvoriti u xml validan element ... pa to joj je posao (znači ruby date u xml node date)
   2. utf8 format mora biti za stringove - to bi se moralo moći ukrasti iz ruby_pdf lib-a gdje smo output iz clipper-a pretvarali u pdf. Mislim da je taj pdf utf8

dobra je stvar što nema nikakvih razloga da ovo bez nervoze privedemo kraju. posla ima da se to ispegla, ali glavne nepoznanice su čiste

kako konvertovati ?¶

čitavo vrijeme razmišljam i par puta sam si postavljao pitanje ? šta bi to bio dobar medij za razmjenu a da ne trošimo vrijeme na parsiranje. Valja formatirati clipper -> txt, pa onda to iščitavati i parsirati u ruby.

Dobro to znamo da je zicer. To smo na hiljade načina radili.

Onda mi je palo na pamet. A zašto ne ubacimo pred_aplikaciju ovom ruby parseru koja će clipper tabele pljunuti u format koji ruby čita normalno.

I tu mi je pao na pamet sqlite. Mala bazica koja ne traži nikakav server (kao mysql ili postgresql ... hehe to bi bilo genijalno - radi konverzije instalirati jedan postgresql ili mysql serverčić ... )

izgleda komplikovano ?

Ako sa harbour-om možemo to uraditi, a prema onome što sam čitao ne bi trebalo biti problema jer ima hbsqlite binding spreman i znam da ga raja koristi masovno, workflow je sljedeći.

1. LD (LD-PKE) unos podataka -> dbf-ove i ništa dalje - no export
2. hb_pke_2_sqlite (provrti kroz dbf-ove i pukne sqlite pke.db koji sadrži sve potrebne tabele koje trebaju xml generatoru)
3. ruby otvori sqlite
   • kvalitetna libs postoje ... koristio sam u rails-u može se via active record orm-a ili direktno sql ... to može da radi

Šta dobijamo: nemamo parsera out - in. samo dumpovanje tabela.

harbour dbfcdx -> sqlite
Ovo ne bi trebao biti problem, lijepa škola harbour-a. Ako bih imao vremna merak bi mi bio da ovo probam.¶

Posebno zato što saši ne bih davao da troši vrijeme na podešavanje harbour build + mingw mislim da je moja dokumentacija samo meni čitljiva, ovo što sam radio od prvog maja.

Dodatno, harbour ima 3-četiri varijante pristupa sqlite-u i ja sam to dosta pratio, pa je dodatni razlog da ja to protabirim.

clipper -> harbour dbfcdx¶

Ionako je moja namjera da čim prije započnemo masovni clipper->harbour port, jer portiranje nemam dileme će biti odlična stvar.

Moramo se kutarisati klipera, obezbjediti istu funkcionalnost koju imamo sa clipper aplikacijama.

Eksperment ? Neka je. Je li ja to tako napamet ? Ne, nije napamet, nakon više od godinu dana konstantnog praćenja harbour mailiste. Harbour je stabilan i zdrav opensource projekat.

Čine ga ex-clipperaši koji su portirali svoje legacy aplikacije i još su pametnice pa sada prave nove stvari u svom omiljenom xbase programerskom dijalektu.

rama-glas linux-desktop¶

možda i da !

cijena LD-PXE-XML LD-PXE¶

Cijena je žara. Četiri puta sam se vraćao na cijenu kad sam pripremao rudnik.

a) E sad kad sam vidio da će ljudi imati mogućnost direktnog unosa => još manje potrebe za kupovinom ovog jednokratnog modula ovo bi bilo skroz loša procjena

b) Sada kad sam prošao xml, ma znaš šta mozak da mi gori za 100 KM ... nema šanse. Ovdje treba još brat bratu 15 h da ovo proradi.

Hah, na ovakvim opcijama korisnici moraju kukati. Njima jeste skupo, ali i nama jeste skupo ovo proizvesti.

Mi ovo radimo da zaradimo, a ne da nam kažu: "jeste vi dobri programeri, i još sve džaba ..."

A pored toga klasična vreva od podrške, koja je sigurno još dodatnih 20-30% opterećenja naših resursa.

Hah kad sam počinjao ovaj posao, kada neko kaže: set knjigovodstvenih aplikacija kod njih košta 10 000 KM. Reko pa oni kradu. E moj Ernade ... pojma ti nisi imao ...

FREAK¶

čovječe koji sam ja freak ... ust'o jutros u 04:30 .. tamo negdje oko 18:00 ma samo što nisam zaspo normalno ...

I sad kad sam ovo uradio i kad osjećam da sam uradio nešto dobro (i radio što volim ...) evo me ko nadrogiran. Mog'o bi još nastavit !?

O toj ljubavi prema informatici govorim. Ne o tome da me interesuje samo informatika, a pare nisu bitne.

Pa zar ne vidite da nakon ovih ponuda svi tablete za smirenje uzimaju ... brinem ja o parama, al raja stisla pa ne da :)